-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Song 494 remove analysis ids #533
Conversation
|
||
// Prevent duplicate analyses from being created | ||
checkServer( | ||
!isAnalysisExist(candidateAnalysisId), | ||
!isAnalysisExist(analysisId), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the (very unlikely) even that there is a random number collision, there's nothing the user can do about it.
Either remove the check, or, if you're paranoid enough, wrap it in a while(collision) { generate_new_random_number()} type loop.
@@ -56,20 +57,7 @@ public SubmitResponse submit( | |||
@RequestHeader(value = AUTHORIZATION, required = false) final String accessToken, | |||
@PathVariable("studyId") String studyId, | |||
@RequestBody @Valid String json_payload) { | |||
return uploadService.submit(studyId, json_payload, false); | |||
return uploadService.submit(studyId, json_payload); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should check to make sure the client code and sdk examples match the server changes.
Specifically, I noticed song-python-sdk/examples/example_upload.py, line 76 still has "ignore_analysis_id_collisions" as a parameter to api.save.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for the reminder. I completely forgot lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall! 👍
A couple of small issues -- error handling for random number generation, and double-check the client code/sdk examples still work with the new server API.
Reference Remove the option for user supplied analysisIds #494